home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Internet Tools (InfoMagic)
/
Internet Tools.iso
/
dos_win
/
winsock
/
maillist
/
94-05.Z
/
94-05
/
000278_news@bigblue.oit.unc.edu_Thu May 19 15:58:56 1994.msg
< prev
next >
Wrap
Internet Message Format
|
1994-05-31
|
1KB
Received: from bigblue.oit.unc.edu by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
id AA29434; Fri, 20 May 1994 00:25:10 -0400
Received: by bigblue.oit.unc.edu (AIX 3.2/UCB 5.64/4.03)
id AA32136; Thu, 19 May 1994 23:56:54 -0400
Received: from GATEWAY by bigblue with netnews
for winsock@sunsite.unc.edu (winsock@sunsite.unc.edu)
To: winsock@sunsite.unc.edu
Date: Thu, 19 May 1994 15:58:56 GMT
From: j.c.knowles@cdc.com
Message-Id: <Cq220s.ADp@cdsmail.cdc.com>
Organization: Control Data Systems
Sender: ses
Subject: INVALID_SOCKET on WIN32s
I know that I cannot be the first on to experience this
problem of running WIN32 sockets on WIN32s!!
It seems that the value returned from a failed sock() call
on WIN32s is 0x0000FFFF (at least this is on Novell's and
TCP's winsock implementation.). Thus, the test for failure,
sock() != INVALID_SOCKET (=(~0) =( 0xFFFFFFFF)), will not work!!
What sorts of work arounds have people be using to get around
this problem????
Any and all comments are welcome.
Jonathan Knowles
j.c.knowles@cdc.com